<?xml version="1.0"?>
<doc>
    <assembly>
        <name>TaskManager04</name>
    </assembly>
    <members>
        <member name="T:DotNetNuke.Modules.TaskManager04.View">
            -----------------------------------------------------------------------------
            <summary>
            The View class displays the content
            
            Typically your view control would be used to display content or functionality in your module.
            
            View may be the only control you have in your project depending on the complexity of your module
            
            Because the control inherits from TaskManager04ModuleBase you have access to any custom properties
            defined there, as well as properties from DNN such as PortalId, ModuleId, TabId, UserId and many more.
            
            </summary>
            -----------------------------------------------------------------------------
            <summary>
            ViewTaskManager04 class.
            </summary>
            <remarks>
            Auto-generated class.
            </remarks>
        </member>
        <member name="T:DotNetNuke.Modules.TaskManager04.TaskManager04ModuleBase">
            <summary>
            This base class can be used to define custom properties for multiple controls. 
            An example module, DNNSimpleArticle (http://dnnsimplearticle.codeplex.com) uses this for an ArticleId
            
            Because the class inherits from PortalModuleBase, properties like ModuleId, TabId, UserId, and others, 
            are accessible to your module's controls (that inherity from TaskManager04ModuleBase
            
            </summary>
        </member>
        <member name="M:DotNetNuke.Modules.TaskManager04.View.Page_Load(System.Object,System.EventArgs)">
            -----------------------------------------------------------------------------
            <summary>
            Page_Load runs when the control is loaded
            </summary>
            -----------------------------------------------------------------------------
        </member>
        <member name="T:DotNetNuke.Modules.TaskManager04.Settings">
            -----------------------------------------------------------------------------
            <summary>
            The Settings class manages Module Settings
            
            Typically your settings control would be used to manage settings for your module.
            There are two types of settings, ModuleSettings, and TabModuleSettings.
            
            ModuleSettings apply to all "copies" of a module on a site, no matter which page the module is on. 
            
            TabModuleSettings apply only to the current module on the current page, if you copy that module to
            another page the settings are not transferred.
            
            If you happen to save both TabModuleSettings and ModuleSettings, TabModuleSettings overrides ModuleSettings.
            
            Below we have some examples of how to access these settings but you will need to uncomment to use.
            
            Because the control inherits from TaskManager04SettingsBase you have access to any custom properties
            defined there, as well as properties from DNN such as PortalId, ModuleId, TabId, UserId and many more.
            </summary>
            -----------------------------------------------------------------------------
            <summary>
            Settings class.
            </summary>
            <remarks>
            Auto-generated class.
            </remarks>
        </member>
        <member name="T:DotNetNuke.Modules.TaskManager04.TaskManager04SettingsBase">
            <summary>
            This base class can be used to define custom properties for multiple controls. 
            An example module, DNNSimpleArticle (http://dnnsimplearticle.codeplex.com) uses this for an ArticleId
            
            Because the class inherits from SettingsModuleBase, properties like ModuleId, TabId, UserId, and others, 
            are accessible to your module's controls (that inherity from TaskManager04SettingsBase
            
            </summary>
        </member>
        <member name="M:DotNetNuke.Modules.TaskManager04.Settings.LoadSettings">
            -----------------------------------------------------------------------------
            <summary>
            LoadSettings loads the settings from the Database and displays them
            </summary>
            -----------------------------------------------------------------------------
        </member>
        <member name="M:DotNetNuke.Modules.TaskManager04.Settings.UpdateSettings">
            -----------------------------------------------------------------------------
            <summary>
            UpdateSettings saves the modified settings to the Database
            </summary>
            -----------------------------------------------------------------------------
        </member>
        <member name="T:DotNetNuke.Modules.TaskManager04.Edit">
            <summary>
            EditTaskManager04 class.
            </summary>
            <remarks>
            Auto-generated class.
            </remarks>
            -----------------------------------------------------------------------------
            <summary>
            The EditTaskManager04 class is used to manage content
            
            Typically your edit control would be used to create new content, or edit existing content within your module.
            The ControlKey for this control is "Edit", and is defined in the manifest (.dnn) file.
            
            Because the control inherits from TaskManager04ModuleBase you have access to any custom properties
            defined there, as well as properties from DNN such as PortalId, ModuleId, TabId, UserId and many more.
            
            </summary>
            -----------------------------------------------------------------------------
        </member>
        <member name="M:DotNetNuke.Modules.TaskManager04.Edit.Page_Load(System.Object,System.EventArgs)">
            -----------------------------------------------------------------------------
            <summary>
            Page_Load runs when the control is loaded
            </summary>
            -----------------------------------------------------------------------------
        </member>
        <member name="M:DotNetNuke.Modules.TaskManager04.Components.Task.Fill(System.Data.IDataReader)">
            <summary>
            The user name of the user who last updated the task.  
            </summary>
            <param name = "dr"> </param>
        </member>
        <member name="P:DotNetNuke.Modules.TaskManager04.Components.Task.TaskId">
            <summary>
            TaskId identifies an individual task.  
            </summary>
        </member>
        <member name="P:DotNetNuke.Modules.TaskManager04.Components.Task.TaskName">
            <summary>
            A string with the name of the task.   
            </summary>
        </member>
        <member name="P:DotNetNuke.Modules.TaskManager04.Components.Task.TaskDescription">
            <summary>
            A string with the description of the task. 
            </summary>
        </member>
        <member name="P:DotNetNuke.Modules.TaskManager04.Components.Task.AssignedUserId">
            <summary>
            An integer with the userid of the assigned user for the task.   
            </summary>
        </member>
        <member name="P:DotNetNuke.Modules.TaskManager04.Components.Task.ModuleId">
            <summary>
            The module id of where the task was created and gets displayed.   
            </summary>
        </member>
        <member name="P:DotNetNuke.Modules.TaskManager04.Components.Task.TargetCompletionDate">
            <summary>
            A date for the targeted completion date.   
            </summary>
        </member>
        <member name="P:DotNetNuke.Modules.TaskManager04.Components.Task.CompletedOnDate">
            <summary>
            A date for the actual completion date of the task.   
            </summary>
        </member>
        <member name="P:DotNetNuke.Modules.TaskManager04.Components.Task.CreatedByUserId">
            <summary>
            An integer for the user id of the user who created the task.   
            </summary>
        </member>
        <member name="P:DotNetNuke.Modules.TaskManager04.Components.Task.LastModifiedByUserId">
            <summary>
            An integer for the user id of the user who last updated the task.  
            </summary>
        </member>
        <member name="P:DotNetNuke.Modules.TaskManager04.Components.Task.CreatedOnDate">
            <summary>
            The date the task was created.   
            </summary>
        </member>
        <member name="P:DotNetNuke.Modules.TaskManager04.Components.Task.LastModifiedOnDate">
            <summary>
            The date on which the task was last modified.   
            </summary>
        </member>
        <member name="P:DotNetNuke.Modules.TaskManager04.Components.Task.PortalId">
            <summary>
            The portal where the article resides.  
            </summary>             
        </member>
        <member name="P:DotNetNuke.Modules.TaskManager04.Components.Task.CreatedByUser">
            Read-only props 
        </member>
        <member name="T:DotNetNuke.Modules.TaskManager04.Data.SqlDataProvider">
            -----------------------------------------------------------------------------
            <summary>
            SQL Server implementation of the abstract DataProvider class
            
            This concreted data provider class provides the implementation of the abstract methods 
            from data dataprovider.cs
            
            In most cases you will only modify the Public methods region below.
            </summary>
            -----------------------------------------------------------------------------
        </member>
        <member name="T:DotNetNuke.Modules.TaskManager04.Data.DataProvider">
            -----------------------------------------------------------------------------
            <summary>
            An abstract class for the data access layer
            
            The abstract data provider provides the methods that a control data provider (sqldataprovider)
            must implement. You'll find two commented out examples in the Abstract methods region below.
            </summary>
            -----------------------------------------------------------------------------
        </member>
        <member name="T:DotNetNuke.Modules.TaskManager04.Components.FeatureController">
            -----------------------------------------------------------------------------
            <summary>
            The Controller class for TaskManager04
            
            The FeatureController class is defined as the BusinessController in the manifest file (.dnn)
            DotNetNuke will poll this class to find out which Interfaces the class implements. 
            
            The IPortable interface is used to import/export content from a DNN module
            
            The ISearchable interface is used by DNN to index the content of a module
            
            The IUpgradeable interface allows module developers to execute code during the upgrade 
            process for a module.
            
            Below you will find stubbed out implementations of each, uncomment and populate with your own data
            </summary>
            -----------------------------------------------------------------------------
        </member>
    </members>
</doc>
